Address translation

ABSTRACT

An apparatus, method, system and computer-readable medium are provided for converting traffic of a first communication type to traffic of one or more additional communication types. In some embodiments, the communication types may comprise IP communications, such as IPv4 and IPv6 communications. In some embodiments, multicast communications may be supported. For example, one or more tunnels or channels may be established to support transmitting data, such as content, to one or more destination addresses. In some embodiments, a destination address may be associated with a user device. One or more messages may comprise an address that may be extracted by a device, such as a router, to determine a destination. The one or more messages may comprise a request for service or a request to join a service group.

BACKGROUND

Communications between two or more devices may be implemented orfacilitated via the use of addresses. For example, IPv4 communicationssupport thirty-two (32) bit addresses. Due to the growth and expansionof communication networks, and more particularly, the number of devicesthat now communicate over networks like the Internet, additionalcommunication protocols have been introduced and utilized. For example,IPv6 utilizes one hundred twenty eight (128) bit addresses, therebyexpanding the number of available addresses.

Transitioning communications from a first type (e.g., a first version ofa protocol) to a second type (e.g., a second version of a protocol),such as transitioning from IPv4 to IPv6 communications, may becumbersome. For example, some new or legacy devices, such as legacyhosts, routers, and user devices might not be configured to support IPv6communications. Given the extent and prevalence of such devices, devicemakers and network and service providers may be reluctant to incur thecosts associated with the transition. Such reluctance may delay theadvancement and progress of IPv6 compliant communications. Moreover,even assuming that device makers and network or service providers mightotherwise be inclined to transition to IPv6 communications, theproviders might not have access or control over such communications,devices, or equipment, thereby potentially requiring the providers tocontinue to support IPv4 communications during a transition to IPv6communications. The foregoing shortcomings are identified by thisdisclosure, and address below.

SUMMARY

This summary is not intended to identify critical or essential featuresof the disclosure provided herein, but instead merely summarizes certainfeatures and variations thereof.

In some embodiments, a device may operate as a proxy for converting datatraffic according to a first communication type (e.g., IPv4 datapackets) into traffic according to a second communication type (e.g.,IPv6 data packets), and vice versa. In some embodiments, the device mayserve as an interface between two or more other devices or communicationnetworks, where the two or more communication networks may adhere todifferent communication types, protocols, standards, etc.

In some embodiments, a device may receive one or more messages from aclient device. The one or more received messages may be indicative of arequest for service. The one or more received messages may be indicativeof, or be interpreted as, a request to be enrolled in one or moreservice groups.

In some embodiments, a device may receive data intended for one or moredestinations. The data received at the device may adhere to a firstcommunication type. The one or more destinations may comprise one ormore user or client devices. In some embodiments, the device maymaintain a table to facilitate forwarding or transmitting the data aspart of a tunnel or channel (e.g., a multicast tunnel or channel). Thetable may map a destination address to one or more tunnel interfaces. Insome embodiments, the device may transmit or forward the received datato one or more destination addresses using one or more tunnels. In someembodiments, the transmitted or forwarded data may be directed to thedestination addresses using a second communication type.

Other details and features will also be described in the sections thatfollow.

BRIEF DESCRIPTION OF THE DRAWINGS

Some features herein are illustrated by way of example, and not by wayof limitation, in the figures of the accompanying drawings and in whichlike reference numerals refer to similar elements.

FIG. 1 illustrates an example information distribution network.

FIG. 2 illustrates an example computing device on which the variouselements described herein can be implemented.

FIG. 3 illustrates an architecture demonstrating one or more aspects ofthis disclosure.

FIG. 4 illustrates a method demonstrating one or more aspects of thisdisclosure.

DETAILED DESCRIPTION

Various connections between elements are discussed in the followingdescription. These connections are general and, unless specifiedotherwise, may be for example direct or indirect, wired or wireless, andthis specification is not intended to be limiting in this respect.

In the following description of various illustrative embodiments,reference is made to the accompanying drawings, which form a parthereof, and in which is shown, by way of illustration, variousembodiments in which aspects of the disclosure may be practiced. It isto be understood that other embodiments may be utilized and structuraland functional modifications may be made, without departing from thescope of the present disclosure.

FIG. 1 illustrates an example information distribution network 100 onwhich many of the various features described herein may be implemented.Network 100 may be any type of information distribution network, such assatellite, telephone, cellular, wireless, etc. One example may be anoptical fiber network, a coaxial cable network or a hybrid fiber/coaxdistribution network. Such networks 100 use a series of interconnectedcommunication lines 101 (e.g., coaxial cables, optical fibers, wireless,etc.) to connect multiple premises 102 (e.g., businesses, homes,consumer dwellings, etc.) to a central office or headend 103. Thecentral office 103 may transmit downstream information signals onto thelines 101, and each premises 102 may have a receiver used to receive andprocess those signals.

There may be one line 101 originating from the central office 103, andit may be split a number of times to distribute the signal to variouspremises 102 in the vicinity (which may be many miles) of the centraloffice 103. The lines 101 may include components not illustrated, suchas splitters, filters, amplifiers, etc. to help convey the signalclearly, but in general each split introduces a bit of signaldegradation. Portions of the lines 101 may also be implemented withfiber-optic cable, while other portions may be implemented with coaxialcable, other lines, or wireless communication paths.

The central office 103 may include a termination system (TS) 104, suchas a cable modem termination system (CMTS), which may be a computingdevice configured to manage communications between devices on thenetwork of lines 101 and backend devices such as servers 105-107 (to bediscussed further below). The termination system (TS) may be asspecified in a standard, such as the Data Over Cable Service InterfaceSpecification (DOCSIS) standard, published by Cable TelevisionLaboratories, Inc. (a.k.a. CableLabs), or it may be a similar ormodified device instead. The termination system (TS) may be configuredto place data on one or more downstream frequencies to be received bymodems at the various premises 102, and to receive upstreamcommunications from those modems on one or more upstream frequencies.The central office 103 may also include one or more network interfaces108, which can permit the central office 103 to communicate with variousother external networks 109. These networks 109 may include, forexample, networks of Internet devices, telephone networks, cellulartelephone networks, fiber optic networks, local wireless networks (e.g.,WiMAX), satellite networks, and any other desired network, and theinterface 108 may include the corresponding circuitry needed tocommunicate on the network 109, and to other devices on the network suchas a cellular telephone network and its corresponding cell phones.

As noted above, the central office 103 may include a variety of servers105-107 that may be configured to perform various functions. Forexample, the central office 103 may include a push notification server105. The push notification server 105 may generate push notifications todeliver data and/or commands to the various premises 102 in the network(or more specifically, to the devices in the premises 102 that areconfigured to detect such notifications). The central office 103 mayalso include a content server 106. The content server 106 may be one ormore computing devices that are configured to provide content to usersin the homes. This content may be, for example, video on demand movies,television programs, songs, text listings, etc. The content server 106may include software to validate user identities and entitlements,locate and retrieve requested content, encrypt the content, and initiatedelivery (e.g., streaming) of the content to the requesting user and/ordevice.

The central office 103 may also include one or more application servers107. An application server 107 may be a computing device configured tooffer any desired service, and may run various languages and operatingsystems (e.g., servlets and JSP pages running on Tomcat/MySQL, OSX, BSD,Ubuntu, Redhat, HTML5, JavaScript, AJAX and COMET). For example, anapplication server may be responsible for collecting television programlistings information and generating a data download for electronicprogram guide or interactive program guide listings. Another applicationserver may be responsible for monitoring user viewing habits andcollecting that information for use in selecting advertisements. Anotherapplication server may be responsible for formatting and insertingadvertisements in a video stream being transmitted to the premises 102.Another application server may be responsible for receiving user remotecontrol commands, and processing them to provide an intelligent remotecontrol experience.

An example premises 102 a may include an interface 120. The interface120 may comprise, in one aspect, a modem 110, which may includetransmitters and receivers used to communicate on the lines 101 and withthe central office 103. The modem 110 may be, for example, a coaxialcable modem (for coaxial cable lines 101), a fiber interface node (forfiber optic lines 101), or any other desired modem device. The modem 110may be connected to, or be a part of, a gateway interface device 111.The gateway interface device 111 may be a computing device thatcommunicates with the modem 110 to allow one or more other devices inthe premises 102 a to communicate with the central office 103 and otherdevices beyond the central office. The gateway 111 may be a set-top box(STB), digital video recorder (DVR), computer server, or any otherdesired computing device. The gateway 111 may also include (not shown)local network interfaces to provide communication signals to devices inthe premises 102 a, such as televisions 112, additional STBs 113,personal computers 114, laptop computers 115, wireless devices 116(wireless laptops and netbooks, mobile phones, mobile televisions,personal digital assistants (PDA), etc.), and any other desired devices.Examples of the local network interfaces include Multimedia Over CoaxAlliance (MoCA) interfaces, Ethernet interfaces, universal serial bus(USB) interfaces, wireless interfaces (e.g., IEEE 802.11), Bluetoothinterfaces, and others. In some embodiments, a client device 117 maycommunication with central office 103 via one or more communicationinterfaces, such as network interface 108 and network 109.

FIG. 2 illustrates general hardware elements that can be used toimplement any of the various computing devices discussed above. Thecomputing device 200 may include one or more processors 201, which mayexecute instructions of a computer program to perform any of thefeatures described herein. The instructions may be stored in any type ofcomputer-readable medium or memory, to configure the operation of theprocessor 201. For example, instructions may be stored in a read-onlymemory (ROM) 202, random access memory (RAM) 203, removable media 204,such as a Universal Serial Bus (USB) drive, compact disk (CD) or digitalversatile disk (DVD), floppy disk drive, or any other desired electronicstorage medium. Instructions may also be stored in an attached (orinternal) hard drive 205. The computing device 200 may include one ormore output devices, such as a display 206 (or an external television),and may include one or more output device controllers 207, such as avideo processor. There may also be one or more user input devices 208,such as a remote control, keyboard, mouse, touch screen, microphone,etc. The computing device 200 may also include one or more networkinterfaces, such as input/output circuits 209 (such as a network card)to communicate with an external network 210. The network interface maybe a wired interface, wireless interface, or a combination of the two.In some embodiments, the interface 209 may include a modem (e.g., acable modem), and network 210 may include the communication lines 101discussed above, the external network 109, an in-home network, aprovider's wireless, coaxial, fiber, or hybrid fiber/coaxialdistribution system (e.g., a DOCSIS network), or any other desirednetwork.

Aspects of this disclosure may be implemented to interfacecommunications between two or more network or communications systems. Insome embodiments, an exchange of messages and/or data may be used tofacilitate the communications. In some embodiments, an addressassociated with one or more client devices may be obtained to associatethe client device(s) with one or more tunnels.

FIG. 3 illustrates an architecture demonstrating one or more aspects ofthis disclosure. In some embodiments, the various blocks shown in FIG. 3may be included in, associated with, or implemented in accordance withone or more of the components and devices described above in connectionwith FIGS. 1-2.

A source 302 may generate or otherwise transmit data. The data may beindicative of one or more content items, such as audio content, voice(e.g., VoIP), video content, graphics, pictures, text, emails, instantmessages, etc. In some embodiments, source 302 may be associated withcentral office 103 or servers 105-107 of FIG. 1. In some embodiments,source 302 may include one or more VOD servers configured to delivervideo using IPv4.

A network 308 may include one or more communication or data accessnetworks. In some embodiments, network 308 may adhere to a firstcommunication type, such as IPv4 communications. Network 308 may conveydata received from source 302, or data generated by network 308, to oneor more devices as described further below. In some embodiments, network308 may be associated with network 109 of FIG. 1 or network 210 of FIG.2.

A computing device such as a router 314, such as an Address FamilyTransition Router (AFTR), may function as a proxy to deliver one or moremessages, such as an Internet Group Management Protocol (IGMP) message,to one or more devices, such as one or more routers. For example, router314 may deliver a message from users behind an element 326 to afirst-hop IPv4 multicast router upstream of router 314. In someembodiments, router 314 and/or element 326 may be associated withcentral office 103 or interface 120 of FIG. 1. In some embodiments,element 326 may comprise a broadband element, such as a Basic BridgingBroadBand element (B4).

In some embodiments, router 314 may be included as a bridge to join bothIPv4 and IPv6 multicast (or another transmission scheme) distributiontrees. For example, router 314 may replicate IPv4 multicast streams intoIPv4-in-IPv6 streams in one or more branches of an IPv6 multicastdistribution stream. In some embodiments, router 314 may build orreference a translation tool, such as a mapping table, that maps element326's IPv6 addresses and multicast groups. The table may function as anaccess table to, for example, match a multicast enrollment orsubscription to element 326.

In some embodiments, router 314 may function to translate an IPv4multicast address to an IPv6 multicast address and use join messages(e.g. PIM-JOIN) to join both the IPv4 and IPv6 multicast (or anothertransmission scheme) distribution trees. For example, router 314 maytake the IPv6 multicast address from the PIM message sent by a router innetwork 320 and translate the IPv6 multicast address to the IPv4multicast address. Router 314 may use the IPv4 multicast address to sendthe PIM message to a next-hop router in network 308.

A network 320 may include one or more communication or data accessnetworks. In some embodiments, network 320 may adhere to a secondcommunication type, such as IPv6 communications. In some embodiments,network 320 may be associated with network 109 of FIG. 1 or network 210of FIG. 2.

In some embodiments, element 326 may be included in (e.g., embedded in),or otherwise associated with, a client device, such as a user or clientdevice 332. In some embodiments, element 326 may enforce an InternetGroup Management Protocol-Multicast Listener Discovery (IGMP-MLD)interworking function together with a de-capsulation function ofreceived multicast IPv4-in-IPv6 packets. For example, element 326 mayperform a listener portion of an Internet Group Management Protocol(IGMP) and a host portion of a Multicast Listener Discovery (MLD)protocol on an upstream interface. As a skilled artisan wouldappreciate, IGMP may be used in connection with IPv4 groups (e.g.,multicast groups) and MLD may be used in connection with IPv6 groups(e.g., multicast groups). IGMP and MLD may be used between end systemsto request or otherwise communicate data.

User device 332 may include one or more components for communicatingwith one or more devices, such as source 302. For example, in someembodiments user device 332 may be within a service node or group, suchas a logical service group, associated with source 302. In someembodiments, client device may adhere to one or more communicationtypes. For example, user device 332 may communicate according to IPv6.In some embodiments, user device 332 may be associated with devices112-117 of FIG. 1 or device 200 of FIG. 2. In some embodiments, userdevice 332 may include an IP-TV set-top box configured to receive amulticast stream from source 302 in IPv4.

The architecture of FIG. 3 is illustrative. In some embodiments, otherarchitectures or variations of the architecture shown in FIG. 3 may beused. The various blocks of FIG. 3 may be arranged in any way, and anynumber of communication paths may exist between or amongst the variousblocks. By way of illustration, the dashed lines in FIG. 3 may representalternative communication paths between source 302 and router 314,network 320, element 326, and/or user device 332. Thus, using one ormore of the dashed communication paths, source 302 may communicate withone or more of router 314, network 320, element 326, and/or user device,potentially bypassing network 308. Other communication paths (not shownin FIG. 3) may be used by one or more of the blocks shown in FIG. 3.

FIG. 4 illustrates a method that may be used in conjunction with one ormore aspects of this disclosure. The method of FIG. 4 may be operativein connection with one or more architectures or environments. The methodof FIG. 4 is described below in connection with the architecture of FIG.3 for illustrative purposes only. The method may be adapted toaccommodate other environments or architectures.

The method of FIG. 4 may be used as a proxy for encapsulating IPv4packets or traffic into IPv6 packets or traffic, or vice versa. Forexample, a device (e.g., device 332 of FIG. 3) behind an element ordevice (e.g., element 326 of FIG. 3) may only have an IPv6 address (asopposed to an IPv4 address) associated with it, potentially due to alack of available IPv4 addresses or other reasons. The method of FIG. 4may be used to realize an expansion of a network address space (e.g.,IPv4 to IPv6 compliant communication) without having to fully implementa more advanced communication type (e.g., IPv6).

In step 404, user device 332 may transmit one or more messages. The oneor more messages may be indicative of a request for service, such as arequest for a content item or asset. The one or more messages may betransmitted in response to a user of device 332 indicating that the userwants to join or subscribe to a group, such as an IPv4 multicast group.The one or more messages may comprise an IGMP message. The one or moremessages may be generated by device 332. The one or more messages maycomprise one or more control messages.

In step 410, a network device such as element 326 may receive one ormore messages, such as a message transmitted by user device 332, inconnection with step 404. Element 326 may encapsulate the one or moremessages with a header, such as an IPv6 header. Element 326 may convertone or more messages into a report message, such as an MLD reportmessage. Element 326 may transmit the MLD report message upstream, e.g.,towards source 302.

In step 416, a join message may be triggered or generated. For example,a join message (e.g., a PIM-JOIN) may be triggered by an MLD querier oranother entity (not shown in FIG. 3) in response to receiving the MLDreport message. In some embodiments, the join message may be indicativeof a communication type, such as IPv6. The join message may betransmitted to one or more devices or entities.

In step 422, the join message of step 416 may be received by one or moreentities. For example, the join message may be received by a computingdevice, such as a router 314. Router 314 may extract a group address(e.g., an IPv4 multicast group address) from the join message and maytransmit the join message, or a portion thereof, upstream, e.g., towardsource 302. In this regard, communications between router 314 anddevices upstream from router 314 (e.g., source 302) may adhere to afirst communication type (e.g., IPv4), and communications between router314 and devices downstream from router 314 (e.g., user device 332) mayadhere to a second communication type (e.g., IPv6).

In step 428, source 302 (or another entity not shown in FIG. 3) mayreceive the join message, or a portion thereof, transmitted inconnection with step 422. In response to the message, source 302 (oranother entity) may provide service to user device 332. For example, aspart of step 428, source 302 (or another entity) may enroll user device332 in a service group, provide or transmit a content item or asset,etc.

In step 434, source 302 may transmit data to router 314. The data may betransmitted in response to the (portion of the) join message received inconnection with step 428. The transmitted data may fulfill a servicerequest initiated by user device 332 (e.g., where the service requestmay be indicated by one or more of the messages transmitted inconnection with step 404).

In step 440, router 314 may receive the data transmitted in connectionwith step 434 and may prepare the data for transmission over network320, where network 320 may adhere to IPv6 communications.

In some embodiments, as part of step 440, router 314 may associate oneor more tunnel interfaces, such as logical tunnel interfaces, to createa multicast tunnel or channel, or a unicast tunnel or channel, oranother type of communication/transmission path. One or more devices mayencapsulate data packets according to a first communication type (e.g.,IPv4) into packets of a second communication type (e.g., IPv6). One ormore devices may transmit the encapsulated data packets according to thesecond communication type to one or more other devices, such as adownstream multicast enabled router configured in accordance with thesecond communication type, via the tunnel

In some embodiments, data received at router 314 from an upstream device(e.g., source 302) may include an indication of the tunnel itself or anintended destination (e.g., user device 332, or an address of userdevice 332). Responsive to receiving data with such an indication,router 314 may convert such data to a particular communication type(e.g., IPv6) and transmit the data to the destination device(s) in thatform. Router 314 may maintain a table in memory to facilitate mapping adestination device to one or more tunnels or channels. For example,router 314 may maintain a mapping of an address associated with adestination device to one or more tunnels or channels.

The method of FIG. 4 is illustrative. In some embodiments, some of thesteps (or portions thereof) may execute in an order different from whatis shown. In some embodiments, some of the steps (or portions thereof)may be optional. In some embodiments, one or more additional steps notshown may be included.

While some examples have been described above in the context of InternetProtocol (IP) technology and communications, aspects of this disclosuremay readily be applied to other forms and types of communication. Thevarious forms of communication may be operative in connection with oneor more television networks, computer networks, satellite networks,cellular networks, etc., in any potential combination.

Although not required, various aspects described herein may be embodiedas a method, a system, an apparatus, and/or as a transitory and/ornon-transitory computer-readable medium storing executable instructions.Accordingly, those aspects may take the form of an entirely hardwareembodiment, an entirely software embodiment, an entirely firmwareembodiment, or an embodiment combining software, firmware, and/orhardware. The functionality may be resident in a single computing deviceor application, or may be distributed across multiple computingdevices/platforms or applications, the multiple computingdevices/platforms optionally being connected to one another via one ormore networks. Moreover, the structural components described herein maybe distributed amongst one or more devices, optionally within a commonhousing or casing.

Various signals representing content, data, or events as describedherein may be transferred between a source and a destination in the formof electromagnetic waves traveling through signal-conducting media suchas metal wires, optical fibers, and/or wireless transmission media(e.g., air and/or space).

The methods and processes described herein may be tied to particularmachines or apparatuses. For example, as described herein, a router mayinterface communications between two or more entities using two or morecommunication types. More generally, one or more apparatuses may includeone or more processors and memory storing instructions that, whenexecuted by the one or more processors, cause the one or moreapparatuses to perform the methodological acts and processes describedherein. Furthermore, the methodological acts and processes describedherein may perform a variety of functions including transforming anarticle (e.g., messages and/or data in accordance with a firstcommunication type) into a different state or thing (e.g., messagesand/or data in accordance with a second communication type).

Aspects of the disclosure have been described in terms of illustrativeembodiments thereof. While illustrative systems and methods as describedherein embodying various aspects of the present disclosure are shown, itwill be understood by those skilled in the art, that the disclosure isnot limited to these embodiments. Modifications may be made by thoseskilled in the art, particularly in light of the foregoing teachings.For example, each of the features of the aforementioned illustrativeexamples may be utilized alone or in combination or subcombination withelements of the other examples. For example, any of the above describedsystems and methods or parts thereof may be combined with the othermethods and systems or parts thereof described above in any order. Itwill also be appreciated and understood that modifications may be madewithout departing from the true spirit and scope of the presentdisclosure. The description is thus to be regarded as illustrativeinstead of restrictive on the present disclosure.

What is claimed is:
 1. An apparatus comprising: at least one processor;and a memory storing instructions that, when executed by the at leastone processor, cause the apparatus to: receive a control messageaccording to IPv6 communications, extract an address indicative of IPv4communications based on the message, and transmit at least a portion ofthe message according to the extracted address.
 2. The apparatus ofclaim 1, wherein the received message is encapsulated with an IPv6header.
 3. The apparatus of claim 1, wherein the transmitted at least aportion of the message comprises a request for service, and wherein theinstructions, when executed by the at least one processor, cause theapparatus to: receive data responsive to the request for service.
 4. Theapparatus of claim 3, wherein the received data adheres to IPv4communications, and wherein the instructions, when executed by the atleast one processor, cause the apparatus to: convert or encapsulate thereceived IPv4 data to adhere to IPv6 communications, and transmit theconverted or encapsulated data.
 5. The apparatus of claim 1, wherein theinstructions, when executed by the at least one processor, cause theapparatus to: maintain data mapping a user device to the apparatus viaat least one tunnel, and maintain in the data mapping the user device tothe apparatus a mapping of an extracted address to the at least onetunnel
 6. The apparatus of claim 5, wherein the at least one tunnelcomprises a logical tunnel, and wherein the extracted address isassociated with a data source, and wherein the instructions, whenexecuted by the at least one processor, cause the apparatus to: receivedata, wherein the received data comprises an indication of the logicaltunnel, and transmit the received data toward the user device based onthe extracted address and using the logical tunnel
 7. The apparatus ofclaim 6, wherein the logical tunnel is associated with a first servicegroup, and wherein the at least one tunnel comprises a second logicaltunnel, wherein the second logical tunnel is associated with a secondservice group that is at least partially different from the firstservice group, and wherein the instructions, when executed by theprocessor, cause the apparatus to: receive a second message, transmit atleast a portion of the second message, receive second data responsive totransmitting the at least a portion of the second message, transmit thesecond data toward the user device using the second logical tunnel
 8. Amethod comprising: receiving, at an apparatus, a control messageaccording to a first communication type from a user device; extracting,at the apparatus, an address indicative of a second communication typebased on the message, wherein the second communication type is differentfrom the first communication type; and transmitting, from the apparatus,at least a portion of the message according to the extracted address. 9.The method of claim 8, wherein the first communication type comprisesIPv6 communications, and wherein the second communication type comprisesIPv4 communications.
 10. The method of claim 8, wherein the receivedmessage is encapsulated with a header according to the secondcommunication type.
 11. The method of claim 8, further comprising:receiving, at the apparatus, data from a source responsive totransmitting the at least a portion of the message, wherein the receiveddata adheres to the second communication type.
 12. The method of claim11, further comprising: converting or encapsulating the received data tothe first communication type; and transmitting the converted orencapsulated data to the user device based at least in part on theextracted address.
 13. The method of claim 11, further comprising:maintaining data mapping the user device to the apparatus via at leastone tunnel; and transmitting the received data to the user device usingthe at least one tunnel
 14. The method of claim 13, wherein the datamapping the user device to the apparatus comprises data mapping a seconduser device to the apparatus via the at least one tunnel, and whereinthe transmitting of the data to the user device using the at least onetunnel comprises transmitting the data to the second user device usingthe at least one tunnel.
 15. A system comprising: a broadband element;and a router, wherein the broadband element is configured to receive acontrol message according to a first communication type, wherein themessage indicates that a user device requests service, and wherein thebroadband element is configured to encapsulate the message with a headeraccording to a second communication type and transmit the encapsulatedmessage to the router, and wherein the router is configured to extract agroup address according to the second communication type from themessage.
 16. The system of claim 15, wherein the broadband element isconfigured to translate the message to a MLD report message, and whereintransmitting the encapsulated message to the router comprisestransmitting the MLD report message to the router.
 17. The system ofclaim 15, wherein the router is configured to receive data responsive totransmitting the request for service to at least one source.
 18. Thesystem of claim 15, wherein the router is configured to maintain datamapping a group address according to the second communication type and atunnel
 19. The system of claim 18, wherein the router is configured toreceive data and transmit the data based at least in part on the datamapping.
 20. The system of claim 19, wherein the router is configured totransmit the data to the broadband element by encapsulating the dataaccording to the first communication type.